docs(js): Add docs for `strictTraceContinuation` and `orgId` #14459

s1gr1d · 2025-07-25T09:30:43Z

DESCRIBE YOUR PR

Docs for strictTraceContinuation and orgId (related PR).

I'm not 100% sure where I should put the orgId as it does not 100% fit into the "Tracing Options" section but it's currently only used for tracing.

closes getsentry/sentry-javascript#16308

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

Urgent deadline (GA date, etc.):
Other deadline:
None: Not urgent, can wait up to 1 week+

SLA

Teamwork makes the dream work, so please add a reviewer to your PRs.
Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.
Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

Checked Vercel preview for correctness, including links
PR was reviewed and approved by any necessary SMEs (subject matter experts)
PR was reviewed and approved by a member of the Sentry docs team

vercel · 2025-07-25T09:30:48Z

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sentry-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 29, 2025 9:19am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
develop-docs	⬜️ Ignored (Inspect)	Visit Preview		Jul 29, 2025 9:19am

codecov · 2025-07-25T09:34:54Z

Bundle Report

Changes will increase total bundle size by 10.75kB (0.05%) ⬆️. This is within the configured threshold ✅

Detailed changes

Bundle name	Size	Change
sentry-docs-client-array-push	9.83MB	-6 bytes (-0.0%) ⬇️
sentry-docs-server-cjs	12.25MB	10.76kB (0.09%) ⬆️

Affected Assets, Files, and Routes:

view changes for bundle: sentry-docs-client-array-push

Assets Changed:

Asset Name	Size Change	Total Size	Change (%)
`static/chunks/pages/_app-*.js`	-3 bytes	879.71kB	-0.0%
`static/chunks/1831-*.js`	-3 bytes	422.23kB	-0.0%
`static/TWZY_3xasV4uN6CE4ovqv/_buildManifest.js` (New)	684 bytes	684 bytes	100.0% 🚀
`static/TWZY_3xasV4uN6CE4ovqv/_ssgManifest.js` (New)	77 bytes	77 bytes	100.0% 🚀
~~*`static/-.js`*~~ (Deleted)*	-77 bytes	0 bytes	-100.0% 🗑️
~~*`static/-.js`*~~ (Deleted)*	-684 bytes	0 bytes	-100.0% 🗑️

view changes for bundle: sentry-docs-server-cjs

Assets Changed:

Asset Name	Size Change	Total Size	Change (%)
`1729.js`	-3 bytes	1.75MB	-0.0%
`../instrumentation.js`	-3 bytes	1.08MB	-0.0%
`9523.js`	-3 bytes	1.05MB	-0.0%
`../app/[[...path]]/page.js.nft.json`	3.59kB	728.4kB	0.5%
`../app/platform-redirect/page.js.nft.json`	3.59kB	728.31kB	0.5%
`../app/sitemap.xml/route.js.nft.json`	3.59kB	725.79kB	0.5%

s1gr1d · 2025-07-25T09:37:08Z

docs/platforms/javascript/common/configuration/options.mdx

+  <SdkOption name="orgId" type='`${number}` | number'>
+
+    The organization ID for your Sentry project.
+
+    The SDK will try to extract the organization ID from the DSN. If it cannot be found, or if you need to override it,
+    you can provide the ID with this option. The organization ID is used for trace propagation and for features like `strictTraceContinuation`.
+
+  </SdkOption>


As stated in the PR description: I am not 100% sure where we should put orgId in the options hierarchy.

It's fine. Or move it below DSN.

I agree!
Here are my thoughts:
A more sustainable approach (for example, in the future, this ID could be used in other features?) might be to place it under "Core Options", under DSN. Then, to highlight that only specific features use this option, you could put the respective sentences ("The organization ID is used for ...") into an Alert (info). And then link orgId in the strictTraceContinuation option so users don't have to search for it.

cleptric · 2025-07-25T12:04:59Z

docs/platforms/javascript/common/configuration/options.mdx

+  <SdkOption name="orgId" type='`${number}` | number'>
+
+    The organization ID for your Sentry project.
+
+    The SDK will try to extract the organization ID from the DSN. If it cannot be found, or if you need to override it,
+    you can provide the ID with this option. The organization ID is used for trace propagation and for features like `strictTraceContinuation`.
+
+  </SdkOption>


It's fine. Or move it below DSN.

inventarSarah

Looks good to me! ☀️

I added a few suggestions (mostly the same because of the repeating content :) )

inventarSarah · 2025-07-29T08:12:16Z

docs/platforms/javascript/common/configuration/options.mdx

+  <SdkOption name="orgId" type='`${number}` | number'>
+
+    The organization ID for your Sentry project.
+
+    The SDK will try to extract the organization ID from the DSN. If it cannot be found, or if you need to override it,
+    you can provide the ID with this option. The organization ID is used for trace propagation and for features like `strictTraceContinuation`.
+
+  </SdkOption>


I agree!
Here are my thoughts:
A more sustainable approach (for example, in the future, this ID could be used in other features?) might be to place it under "Core Options", under DSN. Then, to highlight that only specific features use this option, you could put the respective sentences ("The organization ID is used for ...") into an Alert (info). And then link orgId in the strictTraceContinuation option so users don't have to search for it.

inventarSarah · 2025-07-29T08:14:55Z

docs/platforms/javascript/common/configuration/options.mdx

+    The organization ID for your Sentry project.
+
+    The SDK will try to extract the organization ID from the DSN. If it cannot be found, or if you need to override it,
+    you can provide the ID with this option. The organization ID is used for trace propagation and for features like `strictTraceContinuation`.


Suggested change

you can provide the ID with this option. The organization ID is used for trace propagation and for features like `strictTraceContinuation`.

you can provide the ID with this option. The organization ID is used for trace propagation and features like `strictTraceContinuation`.

inventarSarah · 2025-07-29T08:18:46Z

platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx

+_Available since SDK version 10_
+
+When your application receives requests, they might include `sentry-trace` and `baggage` headers from an upstream service that is also using Sentry.
+By default, the SDK will continue the trace from the incoming headers. This can be undesirable if the requests are from a third-party service,


Suggested change

By default, the SDK will continue the trace from the incoming headers. This can be undesirable if the requests are from a third-party service,

By default, the SDK will continue the trace from these incoming headers. However, this behavior can be undesirable if the requests are from a third-party service,

inventarSarah · 2025-07-29T08:20:36Z

platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx

+By default, the SDK will continue the trace from the incoming headers. This can be undesirable if the requests are from a third-party service,
+as it can lead to unwanted traces, increased billing, and skewed performance data.
+
+To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks the incoming request for Sentry trace information.


Suggested change

To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks the incoming request for Sentry trace information.

To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks the incoming request for Sentry trace information and only continues the trace if it belongs to the same Sentry organization.

inventarSarah · 2025-07-29T08:20:53Z

platform-includes/distributed-tracing/how-to-use/javascript.nextjs.mdx

+as it can lead to unwanted traces, increased billing, and skewed performance data.
+
+To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks the incoming request for Sentry trace information.
+It only continues the trace if it belongs to the same Sentry organization. Otherwise, it starts a new trace.


Suggested change

It only continues the trace if it belongs to the same Sentry organization. Otherwise, it starts a new trace.

Otherwise, it starts a new trace.

platform-includes/distributed-tracing/how-to-use/javascript.solidstart.mdx

platform-includes/distributed-tracing/how-to-use/javascript.sveltekit.mdx

## DESCRIBE YOUR PR Docs for `strictTraceContinuation` and `orgId` ([related PR](getsentry/sentry-javascript#16313)). I'm not 100% sure where I should put the `orgId` as it does not 100% fit into the "Tracing Options" section but it's currently only used for tracing. closes getsentry/sentry-javascript#16308 ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.):  - [ ] Other deadline:  - [ ] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs)

docs(js): Add docs for strictTraceContinuation and orgId

78c211a

s1gr1d requested review from inventarSarah, mydea and cleptric July 25, 2025 09:31

s1gr1d commented Jul 25, 2025

View reviewed changes

vercel bot deployed to Preview – sentry-docs July 25, 2025 09:46 View deployment

Add notice about availablility

8259976

vercel bot deployed to Preview – sentry-docs July 25, 2025 11:17 View deployment

cleptric approved these changes Jul 25, 2025

View reviewed changes

s1gr1d requested review from Lms24 and codyde July 25, 2025 13:43

inventarSarah approved these changes Jul 29, 2025

View reviewed changes

review suggestions

6b60dfc

vercel bot deployed to Preview – sentry-docs July 29, 2025 09:19 View deployment

s1gr1d merged commit 8436336 into master Jul 29, 2025
13 checks passed

s1gr1d deleted the sig/js-strictTraceContinuation branch July 29, 2025 12:07

github-actions bot locked and limited conversation to collaborators Aug 14, 2025

	you can provide the ID with this option. The organization ID is used for trace propagation and for features like `strictTraceContinuation`.
	you can provide the ID with this option. The organization ID is used for trace propagation and features like `strictTraceContinuation`.

	By default, the SDK will continue the trace from the incoming headers. This can be undesirable if the requests are from a third-party service,
	By default, the SDK will continue the trace from these incoming headers. However, this behavior can be undesirable if the requests are from a third-party service,

	To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks the incoming request for Sentry trace information.
	To prevent this, you can enable `strictTraceContinuation`. When this option is set to `true`, the SDK checks the incoming request for Sentry trace information and only continues the trace if it belongs to the same Sentry organization.

	It only continues the trace if it belongs to the same Sentry organization. Otherwise, it starts a new trace.
	Otherwise, it starts a new trace.

Uh oh!

docs(js): Add docs for strictTraceContinuation and orgId #14459

docs(js): Add docs for strictTraceContinuation and orgId #14459

Uh oh!

Conversation

s1gr1d commented Jul 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

DESCRIBE YOUR PR

IS YOUR CHANGE URGENT?

SLA

PRE-MERGE CHECKLIST

Uh oh!

vercel bot commented Jul 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

codecov bot commented Jul 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Bundle Report

Affected Assets, Files, and Routes:

Assets Changed:

Assets Changed:

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

inventarSarah left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

docs(js): Add docs for `strictTraceContinuation` and `orgId` #14459

docs(js): Add docs for `strictTraceContinuation` and `orgId` #14459

s1gr1d commented Jul 25, 2025 •

edited

Loading

vercel bot commented Jul 25, 2025 •

edited

Loading

codecov bot commented Jul 25, 2025 •

edited

Loading